When provisioning software is used to install the SAS Add-In for Microsoft Office, a component of the installation on Windows 7 and Windows Server 2008 R2 machines might fail. As a result, the SAS menu is missing from the Microsoft Office products.

The problem occurs if the provisioning software uses the SYSTEM account (which is the default in most provisioning software).

In addition to the missing SAS menu, a resulting IT log file (install_msofficeint_6.1_win_en_date-time.log) might show the following:

Workarounds

There are different workarounds for this issue. Which one you use depends on the format of the installation that is being performed with the provisioning package:

• A standard installation, which uses the SAS^® Deployment Wizard
• An independent installation, which is new beginning with SAS^® 9.4 software and is intended for easy distribution of SAS Add-In for Microsoft Office to client machines

Note: These workarounds are to be performed by the provisioning administrator.

Workaround for a Standard, SAS Deployment Wizard Installation

In this workaround, you create and configure a new program that will run with the existing program (the one that is already performing the installation). The new program runs after the installation is complete.

In the first program (the one that performs the installation), it is important to use the -wait option on the command line. Doing so keeps setup.exe resident (in the task list until the SAS Deployment Wizard completes). Here is an example:

In the second program, you create a command line such as the one shown next. Note that this sample path is reflective of 32-bit Office on a 64-bit machine. (The bit architecture of SAS Add-In for Microsoft Office is determined by the bit architecture of Microsoft Office itself.)

SwitcherUtility.exe install61 +EXCEL +WORD +POWERPOINT -OUTLOOK

The "start in" path for the command shown above should be similar to the following path:

Workarounds for an Independent Installation of the SAS Add-In for Microsoft Office

In an independent installation, you (the provisioning administrator) can create a .cmd or .bat file with a "start wait" instruction so that the installation command runs first, followed by the post command that corrects the issue.

Sample command syntax with the "start wait" (start/w) instruction:

start/w "path to the independent installation exe file\SASAddInForMicrosoftOffice61_x86_x64.exe" 
/verysilent -- -responsefile path to response file 

"path to the SAS Add-in installation directory\SwitcherUtility.exe" install61 +EXCEL +WORD +POWERPOINT -OUTLOOK

Sample content in a .bat or .cmd file:

start/w \\servername\sas software depot\standalone_installs\SAS_Add-in_for_Microsoft_Office_Independent_Installer 
\6_1\SASAddInForMicrosoftOffice61_x86_x64.exe /verysilent -- -responsefile c:\amo61ind.txt 

"C:\Program Files (x86)\SASHome\x86\SASAddinforMicrosoftOffice\6.1\SwitcherUtility.exe" install61 +EXCEL +WORD +POWERPOINT -OUTLOOK

An alternative workaround for an independent installation is to mimic the workaround for the SAS Deployment Wizard installation. As with that workaround, you want to have two programs, the first of which runs the main installation command. The -wait parameter must be used with the main installation command to keep setup.exe resident (in the task list until the installation is complete). Consider the following examples and note that the double hyphen is not a mistake.

Sample syntax for command line:

SASAddInForMicrosoftOffice61_x86_x64.exe /verysilent -- -responsefile "path to response file\responsefile" -wait 

The "start in" path for the command shown above should be similar to the following path:

\\servername\sas software depot\standalone_installs\SAS_Add-in_for_Microsoft_Office_Independent_Installer\6_1

The above program runs first, followed by the second program, which should have a command line such as the following: SwitcherUtility.exe install61 +EXCEL +WORD +POWERPOINT -OUTLOOK

The "start in" path for the command shown above should be similar to the following path:

Note: The sample path shown is reflective of 32-bit Microsoft Office on a 64-bit machine. The bit architecture of SAS Add-In for Microsoft Office is determined by the bit architecture of Microsoft Office itself.

For an Installation That Does Not Use the SYSTEM Account

As an alternative, if the provisioned program is configured to run as an account other than SYSTEM, the installation avoids the issue that occurs when the SYSTEM account fails to run the necessary switcher utility command.

Operating System and Release Information